unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-devel@gnu.org
Subject: Re: The Big Switch to Git
Date: Thu, 27 Mar 2008 15:45:59 +0100	[thread overview]
Message-ID: <87myokjkd4.fsf@ambire.localdomain> (raw)
In-Reply-To: fsgb64$e6e$1@ger.gmane.org

() Han-Wen Nienhuys <hanwen@xs4all.nl>
() Thu, 27 Mar 2008 11:28:56 -0300

   this is a non-issue.  You can do the import to a seperate git repo
   later, and then do a merge into core. This will add all the history
   of the side-project to core as well.

   IMO Until there is a need, importing random bitrot is a waste of
   time, and will confuse newcoming hackers.

Sorry, i thought we were talking about parallel Git repos (to reflect the
parallel cvs modules "guile-core", "guile-scripts" and "workbook").  Am
i missing something?

thi





  reply	other threads:[~2008-03-27 14:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 16:23 The Big Switch to Git Ludovic Courtès
2008-03-14 18:38 ` Greg Troxel
2008-03-15 21:30   ` Ludovic Courtès
2008-03-16 20:57     ` Thien-Thi Nguyen
2008-03-24 23:16       ` Neil Jerram
2008-03-27 14:07         ` Thien-Thi Nguyen
2008-03-27 14:28           ` Han-Wen Nienhuys
2008-03-27 14:45             ` Thien-Thi Nguyen [this message]
2008-03-28  4:33               ` Han-Wen Nienhuys
2008-03-28  7:39                 ` Thien-Thi Nguyen
2008-03-28 16:11                   ` Han-Wen Nienhuys
2008-03-28  8:10                 ` Ludovic Courtès
2008-03-28 16:14                   ` Han-Wen Nienhuys
2008-03-15 16:22 ` Thien-Thi Nguyen
2008-03-22  0:41 ` Han-Wen Nienhuys
2008-03-26 22:36   ` Ludovic Courtès
2008-03-24 22:56 ` Neil Jerram
2008-03-26 10:06   ` Ludovic Courtès
2008-03-26 18:47     ` Neil Jerram
2008-03-26 22:31       ` Ludovic Courtès
2008-03-27 20:22         ` Ludovic Courtès
2008-03-27 22:16           ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87myokjkd4.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).