sometimes when merge-ing fast forward doesn't work. but you know what the=20
resolution you want is.
example (current behavior)
Normal merge conflict for 'css/main.css':
{local}: modified
{remote}: modified
Hit return to start merge resolution tool (vimdiff):
but I don't want to. I know the remote updates are right. I could do a git=
=20
checkout remotebranch filename but when you have 20 files that need updatin=
g=20
this is annoying
my suggestion is this
Normal merge conflict for 'css/main.css':
{local}: modified
{remote}: modified
Use (l)local or (r)remote or (m)anual?=20
also in the event of having 20 files with this issue it would be nice to ha=
ve=20
an option after first starting mergetool for remote all or local all.
(note: I am not subscribed to the list)
=2D-=20
Caleb Cushing
my blog http://xenoterracide.blogspot.com| Ian Campbell | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Justin Piszcz | Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195... |
| Alan | Re: [RFC] Heads up on sys_fallocate() |
| Matthias Scheler | Re: HEADS UP: timecounters (branch simonb-timecounters) merged into -current |
| David Laight | long usernames |
| Quentin Garnier | Re: Understanding foo_open, foo_read, etc. |
| Jared D. McNeill | Breaking binary compatibility for /dev/joy |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
