From: "Gustav Hållberg" <gustav@virtutech.com>
To: Karl Wiberg <kha@treskal.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Record a single transaction for conflicting push operations
Date: Mon, 21 Dec 2009 15:31:23 +0100 [thread overview]
Message-ID: <4B2F86BB.9090104@virtutech.com> (raw)
In-Reply-To: <b8197bcb0912210548q67c1da4bhe023bed2811394d4@mail.gmail.com>
On 2009-12-21 14:48, Karl Wiberg wrote:
> I've seen more than one complaint that the current behavior is
> confusing even if we don't count the bug, so I thought this was part
> of the motivation.
I don't know if this would be better than the other suggested solutions,
but if "stg log" would clearly identify multi-stage entries as such, the
current confusion would probably mostly go away.
Currently this is done reasonably well for make_temp_patch(), which says
"refresh (create temporary patch)" in the log, but I think this could be
taken further.
For example, if such annotations said "foo: stage N" or similar,
indicating that this was the Nth step in the "foo" command (think
"rebase" or whatever), it would be good enough for me least.
- Gustav
next prev parent reply other threads:[~2009-12-21 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 23:22 [RFC PATCH] Record a single transaction for conflicting push operations Catalin Marinas
2009-12-18 9:23 ` Karl Wiberg
2009-12-18 15:49 ` Catalin Marinas
2009-12-19 23:50 ` Karl Wiberg
2009-12-20 23:21 ` Catalin Marinas
2009-12-21 7:08 ` Karl Wiberg
2009-12-21 11:48 ` Catalin Marinas
2009-12-21 13:48 ` Karl Wiberg
2009-12-21 14:31 ` Gustav Hållberg [this message]
2009-12-22 18:33 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B2F86BB.9090104@virtutech.com \
--to=gustav@virtutech.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.