git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Norbert Preining <preining@logic.at>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: Creating something like increasing revision numbers
Date: Mon, 19 Oct 2009 03:42:56 +0200	[thread overview]
Message-ID: <20091019014256.GE17397@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <alpine.LFD.2.00.0910182122100.21739@xanadu.home>

On So, 18 Okt 2009, Nicolas Pitre wrote:
> However, given what you want to do is really to stick to the SVN way of 
> doing things, then why don't you simply stay with SVN?  Git works in a 

I fear so.

> fundamentally different way than SVN, and if you aren't willing/able to 
> change your workflow away from the SVN way then there is really not much 
> for you to gain by switching to Git.

Well, as I said in the beginning, the metadata handling of svn is a pain
in huge repositories like ours with thousands of subdirectories of subdirs
of subdirs and 80k+ files. That was the reason I thought about git.

But I am coming to the conclusion that I will use git for my other projects,
but not for that one.

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining                                        Associate Professor
JAIST Japan Advanced Institute of Science and Technology   preining@jaist.ac.jp
Vienna University of Technology                               preining@logic.at
Debian Developer (Debian TeX Task Force)                    preining@debian.org
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
GLASSEL (n.)
A seaside pebble which was shiny and interesting when wet, and which
is now a lump of rock, which children nevertheless insist on filing
their suitcases with after the holiday.
			--- Douglas Adams, The Meaning of Liff

  reply	other threads:[~2009-10-19  1:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 14:41 Creating something like increasing revision numbers Norbert Preining
2009-10-18 15:03 ` Johan Herland
2009-10-18 15:20   ` Norbert Preining
2009-10-18 17:23     ` Johan Herland
2009-10-18 18:16       ` alexandrul
2009-10-19  1:15       ` Nicolas Pitre
2009-10-18 22:47     ` Junio C Hamano
2009-10-19  0:48       ` Norbert Preining
2009-10-18 15:29 ` alexandrul
2009-10-18 15:37   ` demerphq
2009-10-18 15:45     ` Norbert Preining
2009-10-18 16:16       ` demerphq
2009-10-18 16:35         ` alexandrul
2009-10-18 15:37 ` Jon Smirl
2009-10-18 21:43 ` Daniel Barkalow
2009-10-19  0:44   ` Norbert Preining
2009-10-19  1:16     ` Daniel Barkalow
2009-10-19  1:33       ` Norbert Preining
2009-10-19  2:41         ` Daniel Barkalow
2009-10-19  1:34     ` Nicolas Pitre
2009-10-19  1:42       ` Norbert Preining [this message]
2009-10-19  6:21     ` Johannes Sixt
2009-10-21  7:47     ` David Aguilar

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=20091019014256.GE17397@gamma.logic.tuwien.ac.at \
    --to=preining@logic.at \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=nico@fluxnic.net \
    /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).