git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Cc: "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 17:30:11 +0200	[thread overview]
Message-ID: <vpqiqrt3mgs.fsf@bauges.imag.fr> (raw)
In-Reply-To: <fcaeb9bf0810150754s613f2c44pd8341711d9d73f73@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Wed\, 15 Oct 2008 21\:54\:26 +0700")

"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?

-- 
Matthieu

  reply	other threads:[~2008-10-15 15:47 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     ` Matthieu Moy [this message]
2008-10-15 16:42       ` [gambit-list] " Michael J Gruber
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=vpqiqrt3mgs.fsf@bauges.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=Gambit-list@iro.umontreal.ca \
    --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).