From: "Marco Costalba" <mcostalba@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: qgit: added "Renames following" in annotation
Date: Fri, 6 Jul 2007 22:53:28 +0200 [thread overview]
Message-ID: <e5bfff550707061353g2a84afa3nf5b9accda274cfd7@mail.gmail.com> (raw)
I've just pushed (git://git.kernel.org/pub/scm/qgit/qgit4.git) a patch
series that add "renames following" to file annotation in qgit
preserving the non-linear (graph) history.
The most interesting cases in git tree are:
builtin-fsck.c (multiple renames)
builtin-mailinfo.c (multiple renames and changed directory)
git-clone.sh (nice history graph)
but the coolest is by far builtin-tar-tree.c where the file has been
renamed from tar- tree.c to builtin-tar-tree.c in _two_ different
commits on _two_ different branches then merged togheter in commit
1af0d11283...
To handle the latest one, a cool generalization has been necessary.
I have tested with _all_ the git files, and it seems to work in all the cases.
Have fun
Marco
reply other threads:[~2007-07-06 20:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e5bfff550707061353g2a84afa3nf5b9accda274cfd7@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).