git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to check out the repository at a particular point in time

From
Jens Lehmann <jens.lehmann@web.de>
Date
Aug 23, 2011, 20:30 UTC
Message-ID
<4E540E02.1060201@web.de>
In-Reply-To
<CAJsNXTk0LaSDKCOzJgZRLYmGe8hauPbPOw4oKLKP0Xr0axZkwg@mail.gmail.com>
Am 23.08.2011 12:04, schrieb PJ Weisberg:
Show 10 quoted lines
> 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.

Previous: PJ Weisberg
Message 4 of 4 in “Re: How to check out the repository at a particular point in time”
  1. R. DiezAug 23, 2011
  2. Thomas RastAug 23, 2011
  3. PJ WeisbergAug 23, 2011
  4. Jens LehmannAug 23, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.