>> Much easier to edit the textual patch visually, then git am.
I never manually edited patches! I use "git mergetool" after a rebase
failure which brings up vim in 4 windows. Then it is a matter of editing a
file in vim with all your usual vim commands. I know, it is important to
know one 'workflow' very well and stick to it.
Regards, Malahal.
On Mon, Jun 5, 2017 at 1:57 PM, William Allen Simpson <
william.allen.simp...@gmail.com> wrote:
> On 6/3/17 3:56 PM, Malahal Naineni wrote:
>
>> I don't understand why you need to keep patches when git gives you the
>> power to store your code in its own branches/stashes. Arguably, git commits
>> have more information than a simple patch diff.
>> That's why I use git format-patch. The default directory is the top of
>>
> the git repository. All patches there should be ignored.
>
> I know I'm an old fuddy-duddy, but I've been using git practically since
> it was released -- for kernel and dARPA projects. So I'm probably using
> older techniques, such a preparing my patch series for email as was
> originally intended.
>
> Moreover, I don't find keeping a lot of branches and commits around in
> the git tree very helpful. Many of my patches here are 2 years old and
> need a lot of massaging to re-commit. So rebase causes a lot of pain.
>
> Much easier to edit the textual patch visually, then git am.
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
