From: Jens Lehmann <Jens.Lehmann@web.de>
To: PJ Weisberg <pjweisberg@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
rdiezmail-temp2@yahoo.de,
"git@vger.kernel.org" <git@vger.kernel.org>,
"in-git-vger@baka.org" <in-git-vger@baka.org>
Subject: Re: How to check out the repository at a particular point in time
Date: Tue, 23 Aug 2011 22:30:58 +0200 [thread overview]
Message-ID: <4E540E02.1060201@web.de> (raw)
In-Reply-To: <CAJsNXTk0LaSDKCOzJgZRLYmGe8hauPbPOw4oKLKP0Xr0axZkwg@mail.gmail.com>
Am 23.08.2011 12:04, schrieb PJ Weisberg:
> On Tue, Aug 23, 2011 at 2:17 AM, Thomas Rast <trast@student.ethz.ch> wrote:
>
>> I personally think that's crazy and -- if you want to avoid the work
>> of "really" using submodules -- support Jens's suggestion of having
>> the buildbot automatically assemble an "I tested this" superproject.
>
> Or create a tag in each separate repository, using the same tag name
> to indicate versions that were tested together. Or you could do the
> same with a branch, since a branch is basically a tag that moves. You
> would just have to make sure only the buildbot updated that branch.
That would also work, but it might need some scripting. Probably having
some server side hooks to enforce the policy allowing no-one except the
buildbot to change those branches/tags would help here. Also submodules
would make it easier to see when they differ from the commits recorded
in the superproject, so a script running something like "git describe"
in all local repos and displaying the results might be a good idea to
get that information.
next prev parent reply other threads:[~2011-08-23 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 7:41 How to check out the repository at a particular point in time R. Diez
2011-08-23 9:17 ` Thomas Rast
2011-08-23 10:04 ` PJ Weisberg
2011-08-23 20:30 ` Jens Lehmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-22 12:25 R. Diez
2011-08-22 13:25 ` Thomas Rast
2011-08-22 15:18 ` R. Diez
2011-08-22 16:56 ` Jens Lehmann
2011-08-23 15:54 ` Michael Witten
2011-08-23 16:05 ` Jonathan Nieder
2011-08-23 16:09 ` Matthieu Moy
2011-08-23 16:23 ` Michael Witten
2011-08-23 16:53 ` Jonathan Nieder
2011-08-24 15:41 ` Andreas Ericsson
2011-08-24 15:48 ` Randal L. Schwartz
2011-08-24 16:18 ` Michael Witten
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=4E540E02.1060201@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=in-git-vger@baka.org \
--cc=pjweisberg@gmail.com \
--cc=rdiezmail-temp2@yahoo.de \
--cc=trast@student.ethz.ch \
/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).