From: Michael J Gruber <git@drmicha.warpmail.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Christian Jaeger <christian@pflanze.mine.nu>,
Git Mailing List <git@vger.kernel.org>,
Marc Feeley <feeley@iro.umontreal.ca>,
Gambit List <Gambit-list@iro.umontreal.ca>
Subject: Re: [gambit-list] Separating generated files? (Re: Mercurial -> git)
Date: Wed, 15 Oct 2008 18:42:31 +0200 [thread overview]
Message-ID: <48F61D77.3080100@drmicha.warpmail.net> (raw)
In-Reply-To: <vpqiqrt3mgs.fsf@bauges.imag.fr>
Matthieu Moy venit, vidit, dixit 15.10.2008 17:30:
> "Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:
>
>> Hi Christian,
>>
>> The idea of using two separate repositories for source and generated
>> source is interesting. I would like to bring this to git mailing list,
>> they may provide insightul comments for your idea or even other
>> approaches.
>
> I think the first question is: do you (and why) need to use a version
> control system for generated files?
I guess we can take "yes" for granted for the first part ;)
As for the why: In cases like this one it's interesting to compare
(read: diff) the output generated by different versions of the input.
I wonder whether a clever use of "excludes" and GIT_DIR would allow
tracking the different filesets in the same dir, but using different
repos. I'm just afraid it's a fragile setup, in the sense that it relies
on config stuff which is not tracked (and thus not reproduced
automatically on clone).
Michael
next prev parent reply other threads:[~2008-10-15 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E6D34628-783D-4597-8B00-C10F27F63BE2@iro.umontreal.ca>
[not found] ` <48F5D86B.6040501@pflanze.mine.nu>
2008-10-15 14:54 ` Separating generated files? (Re: Mercurial -> git) Nguyen Thai Ngoc Duy
2008-10-15 15:30 ` [gambit-list] " Matthieu Moy
2008-10-15 16:42 ` Michael J Gruber [this message]
2008-10-15 17:28 ` Christian Jaeger
2008-10-16 12:00 ` [gambit-list] Separating generated files? Christian Jaeger
2008-10-16 12:12 ` Santi Béjar
2008-10-16 12:32 ` Christian Jaeger
2008-10-16 13:29 ` Santi Béjar
2008-10-15 16:45 ` Christian Jaeger
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=48F61D77.3080100@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Gambit-list@iro.umontreal.ca \
--cc=Matthieu.Moy@imag.fr \
--cc=christian@pflanze.mine.nu \
--cc=feeley@iro.umontreal.ca \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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 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).