* Linus Torvalds torva...@linux-foundation.org wrote:
On Wed, Oct 24, 2012 at 12:25 AM, Thomas Gleixner t...@linutronix.de wrote:
It is spelled:
git notes add -m comment SHA1
Cool!
Don't use them for anything global.
Use them for local codeflow, but don't expect them to be
Am 10/24/2012 0:23, schrieb Jeff King:
For the fold-on-rebase idea, I'd think you would want something similar,
like setting rebase.foldNotes to foo to say refs/notes/foo contains
pseudo-headers that should be folded in like a signed-off-by.
If you are rebasing anyway, you can already use
On Tue, Oct 23, 2012 at 10:22:45PM +0100, Jeff King wrote:
On Tue, Oct 23, 2012 at 10:09:46PM +0100, Catalin Marinas wrote:
It is spelled:
git notes add -m comment SHA1
The resulting notes are stored in a separate revision-controlled branch
and can be pushed and pulled like
Jeff King wrote:
On Tue, Oct 23, 2012 at 11:25:06PM +0200, Thomas Gleixner wrote:
The resulting notes are stored in a separate
revision-controlled branch
Which branch(es) is/are that ? What are the semantics of that?
[...]
Nice feature.
Can a later commit be eventually be made to
On Tue, 23 Oct 2012, Al Viro wrote:
On Tue, Oct 23, 2012 at 01:30:26PM -0400, Chris Metcalf wrote:
I fetched the series from your arch-tile branch and built it, and it works
fine. It looks good from my inspection:
Acked-by: Chris Metcalf cmetc...@tilera.com
Thanks; Acked-by
On Tue, Oct 23, 2012 at 10:47:28PM +0200, Thomas Gleixner wrote:
I agree that this is a common issue. Acked-by/Reviewed-by mails come
in after the fact that the patch has been committed to an immutable
(i.e no-rebase mode) branch or if the change in question already hit
Linus tree.
Still
On 23 October 2012 21:51, Jeff King p...@peff.net wrote:
On Tue, Oct 23, 2012 at 10:47:28PM +0200, Thomas Gleixner wrote:
I agree that this is a common issue. Acked-by/Reviewed-by mails come
in after the fact that the patch has been committed to an immutable
(i.e no-rebase mode) branch or if
On Tue, Oct 23, 2012 at 10:09:46PM +0100, Catalin Marinas wrote:
It is spelled:
git notes add -m comment SHA1
The resulting notes are stored in a separate revision-controlled branch
and can be pushed and pulled like regular refs. Note, though, that the
default refspecs do not yet
On Tue, 23 Oct 2012, Jeff King wrote:
On Tue, Oct 23, 2012 at 10:47:28PM +0200, Thomas Gleixner wrote:
I agree that this is a common issue. Acked-by/Reviewed-by mails come
in after the fact that the patch has been committed to an immutable
(i.e no-rebase mode) branch or if the change in
On Tue, Oct 23, 2012 at 11:25:06PM +0200, Thomas Gleixner wrote:
The resulting notes are stored in a separate revision-controlled branch
Which branch(es) is/are that ? What are the semantics of that?
They are stored in refs/notes/commits by default, but you can have
multiple notes refs if
On Tue, Oct 23, 2012 at 03:06:59PM -0700, Marc Gauthier wrote:
Can a later commit be eventually be made to reference some set
of notes added so far, so they become part of the whole history
signed by the HEAD SHA1? hence pulled/pushed automatically as
well. Otherwise do you not end up with
On Wed, Oct 24, 2012 at 12:25 AM, Thomas Gleixner t...@linutronix.de wrote:
It is spelled:
git notes add -m comment SHA1
Cool!
Don't use them for anything global.
Use them for local codeflow, but don't expect them to be distributed.
It's a separate flow, and while it *can* be
On Wed, Oct 24, 2012 at 04:02:49AM +0300, Linus Torvalds wrote:
On Wed, Oct 24, 2012 at 12:25 AM, Thomas Gleixner t...@linutronix.de wrote:
It is spelled:
git notes add -m comment SHA1
Cool!
Don't use them for anything global.
Use them for local codeflow, but don't expect them
On Wed, Oct 24, 2012 at 4:56 AM, Al Viro v...@zeniv.linux.org.uk wrote:
How about git commit --allow-empty, with
belated ACK for commit
Don't bother. It's not that important, and it's just distracting.
It's not like this is vital information. If you pushed it out without
the ack, it's out
14 matches
Mail list logo
