From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: Meta-commits and subprojects
Date: Tue, 27 Mar 2007 13:44:55 +0200 [thread overview]
Message-ID: <20070327114455.GB12178@informatik.uni-freiburg.de> (raw)
Hello,
just a (maybe silly) idea ...
If the toplevel tree were a subproject (i.e. a commit) you could
represent rebases and other commit reorderings in history. Maybe that's
a feature stgit could exploit?
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=12+mol+in+dozen
reply other threads:[~2007-03-27 11:45 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=20070327114455.GB12178@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--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).