public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Elena Zannoni <elena.zannoni@oracle.com>
To: frysk <frysk@sourceware.org>
Subject: meeting notes 20070905
Date: Wed, 05 Sep 2007 14:22:00 -0000	[thread overview]
Message-ID: <46DEBB8C.6090608@oracle.com> (raw)

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



[-- Attachment #2: frysk-20070905 --]
[-- Type: text/plain, Size: 2544 bytes --]

Frysk meeting 2007-09-05

Version control systems discussions

Tim Andrew Elena Stan Mark Sami [who else?]

Do people that prefer strongly one system have played around with the
others as well?

Tim --> likes Git, hasn't tried Hg
Mark --> Hg

See comparisons posted to mailing list by Mark.


overseers of sourceware.org, what's their take? Would anybody among
them be willing to administer the git/hg stuff. Is there somebody
knowledge there to use as point of reference.

Mark: would stay with cvs, because it's the evil we know. Need to have
somebody to know well how to do the day to day stuff with Hg or Git.
Imports, commits, setting up emails, cutting branches, etc. Mark
hasn't worked enough with any of them to know which system is
safer. He doesn't know well either of them.  How to translate the
current procedures for imports and branches into the new git or hg
framework. 

freedesktop has a split repositories. Developers have personal
repositories where they post their stuff/wip so that it's accessible
to everyone.

having a better scs would allow to have a deamon working through the
head of trunk testing each changeset. as they get committed.

notification: hot to check what's going in? frysk-cvs works well now.
Do those systems have the same stuff? Potential to include the patch
in the email, instead of the link. 

Impact on the history before the switch: it is maintained. No loss of
info there doing the import. 

Import into git from cvs preserved branches. Tim hasn't ported the
history though. Git got confused at some branch merge points in the
history. Tim corrected by hand. Since the first import there were no
more conflicts. Tim does imports/resyncs twice a day, never seen
further problems. Mark observed some problems also when he did import
imnto Hg.

Tim kept 2 repos, one using symbolic links. Mark had to do the same
stuff in Hg.  Frysk-common is the module that presented problems.

Plugins: cvs plugin in eclipse. No other plugins for eclipse.
cvs module in emacs as well. no emacs modes for git and Hg.


Advantage over cvs is that one can recover easily from erroneous
commits, because of the changesets.


What projects we know of are using Git and which ones are using Hg?

Git: kernel, libunwind
Hg: icedtea, openjdk, mozilla


There will be a new page in the website listing pros/cons of the two
systems. People need to fill it in.
http://sourceware.org/frysk/vc/

Expertize in house with each system? Oracle has a few git projects
already and no Hg. How about Rht?


No meeting next week. 




             reply	other threads:[~2007-09-05 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 14:22 Elena Zannoni [this message]
2007-09-05 14:41 ` Phil Muldoon
2007-09-07  7:38 ` Tim Moore

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=46DEBB8C.6090608@oracle.com \
    --to=elena.zannoni@oracle.com \
    --cc=frysk@sourceware.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).