Thread (4 messages) 4 messages, 4 authors, 2016-06-15

Re: [PATCH v9] Documentation/remote-helpers: Add invocation section

From: Ramkumar Ramachandra <hidden>
Date: 2016-06-15 22:48:34

Hi,

On Thu, Apr 8, 2010 at 4:19 AM, Jonathan Nieder [off-list ref] wrote:
Thank you for this.  FWIW I find it useful when discussing a piece of
code or documentation to bounce back and forth multiple versions of
small fragments.  Then once the discussion has settled down, it can be
useful to see the big picture again, with the new changes
incorporated.
Got it. In future, I'll post diffs for smaller changes hopefully in
the same email thread, and complete patches for larger changes in a
separate email thread. I've been quite haphazard in the past.
If you want to make sure the latest version of a patch is always
available, that is a noble goal, too, but I think a frequently-
rebased public branch for your patch series is a better way to achieve
that.
Ah, I already do that, but my branch is based on `pu`. What should I do?
http://github.com/artagnon/git

On Thu, Apr 8, 2010 at 4:32 AM, Junio C Hamano [off-list ref] wrote:
At least it would be helpful for me if people based their follow-up
patches on top of their own topics.
Can I see the topic branch corresponding to my patches? If this is
possible, I can avoid the more painful procedure of extracting it from
the latest pu using git-resurrect.sh.

-- Ram
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help