All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-grub@schottelius.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: VCS [Was: Linux/ADFS partition table support]
Date: Sun, 27 Nov 2005 22:06:02 +0100	[thread overview]
Message-ID: <20051127210602.GD13283@schottelius.org> (raw)
In-Reply-To: <877jbclelh.fsf@student.han.nl>

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

Sorry to misuse this thread, but I've a small question to this
regarding something different, the VCS (version control system):

Marco Gerards [Sun, Nov 13, 2005 at 05:03:38PM +0100]:
> [...]
> Please include the Changelog entry every time you send in a patch,
> otherwise I can't reply to in the a single mail.  I've included it
> this time

Wouldn't it be much easier, if we work with a distributed VCS like
monotone, arch or git? This way people can do their work, we can
pull it or modify it much better than in discussing code on the ML.

This way you could easily move acorn.c to another place without needing
to modify the patch, simply move it in your tree.

It's my general idea to let people do the work how they want to do and
if they want their code in a mainstream project they or we have to simply
include it with our coding standards. And this process, again imho,
is much better supported by distributed version control systems.

Nico

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2005-11-27 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 14:47 Linux/ADFS partition table support Timothy Baldwin
2005-11-08 19:20 ` Timothy Baldwin
2005-11-13 16:03   ` Marco Gerards
2005-11-13 18:51     ` Timothy Baldwin
2005-11-13 19:47       ` Marco Gerards
2005-11-27 21:06     ` Nico -telmich- Schottelius [this message]
2005-11-27 22:17       ` VCS [Was: Linux/ADFS partition table support] Hollis Blanchard
2005-11-23  2:45 ` Linux/ADFS partition table support Hollis Blanchard

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=20051127210602.GD13283@schottelius.org \
    --to=nico-linux-grub@schottelius.org \
    --cc=grub-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.