Jonathan Nieder [off-list ref] writes:
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.
Unrelated: in case you are interested, the git-resurrect.sh script
from contrib can extract topic branches from pu, if you want to see
Junio’s topic branch for your patch.
It might look unrelated, but I found it the most helpful information in
your message ;-) I really hate it when people base their patches on 'pu'.
At least it would be helpful for me if people based their follow-up
patches on top of their own topics.
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
Ramkumar Ramachandra wrote:
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.
I tend to do the extraction by hand:
1. git log --first-parent origin/pu
2. Search for "rr/".
3. git branch -f rr/whatever <relevant sha1>
Maybe it would be nice to have a script that does just that instead of
the more costly "git resurrect -m rr/whatever".
Cheers,
Jonathan
Heya,
On Thu, Apr 8, 2010 at 01:02, Junio C Hamano [off-list ref] wrote:
It might look unrelated, but I found it the most helpful information in
your message ;-) I really hate it when people base their patches on 'pu'.
At least it would be helpful for me if people based their follow-up
patches on top of their own topics.
Hmmm, perhaps we should update SubmittingPatches to say something
about that? The section that talks about what to base your patch
against [0] is not very explicit in that aspect.
[0] http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/SubmittingPatches#l106
--
Cheers,
Sverre Rabbelier