git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abscissa <bus_nabble_git@semitwist.com>
To: git@vger.kernel.org
Subject: Re: SVN -> Git *but* with special changes
Date: Wed, 28 Sep 2011 11:03:45 -0700 (PDT)	[thread overview]
Message-ID: <1317233025014-6841234.post@n2.nabble.com> (raw)
In-Reply-To: <16808473.33899.1317229852319.JavaMail.root@mail.hq.genarts.com>

>> 1. Directories can exist even if there's nothing in them (just like
>> any filesystem).
>
>What requires the empty directories to exist?  The build system?

Yes.

>Can you just let them go away in Git and fix it downstream in the user's
working copy?

That won't work retroactively for already-existing revisions. I'd rather not
break the build system for older revisions just for such a goofy reason as
empty dirs being deemed unnecessary.


--
View this message in context: http://git.661346.n2.nabble.com/SVN-Git-but-with-special-changes-tp6840904p6841234.html
Sent from the git mailing list archive at Nabble.com.

  parent reply	other threads:[~2011-09-28 18:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 16:37 SVN -> Git *but* with special changes Abscissa
2011-09-28 17:10 ` Stephen Bash
2011-09-28 17:44   ` Matthieu Moy
2011-09-28 19:07     ` Jeff King
2011-09-28 18:03   ` Abscissa [this message]
2012-01-07 22:30   ` Abscissa
2011-09-28 19:04 ` Jeff King
2012-01-08  5:03   ` Abscissa
2012-01-08  5:10     ` Jeff King
2012-01-08  5:17       ` Abscissa
2012-01-08  5:25         ` Abscissa
2012-01-08 10:33           ` Carlos Martín Nieto
2012-01-08 10:47             ` Andreas Schwab
2012-01-08 12:08               ` Adam Borowski
2012-01-08 22:28                 ` Abscissa
2012-01-08 23:38                   ` Abscissa
2012-01-12 21:52                     ` Abscissa
2012-01-14  3:43                       ` Abscissa
2012-01-09  8:26                   ` Michael Haggerty
2012-01-08 11:24           ` Thomas Hochstein
2012-01-08 11:20         ` Thomas Hochstein

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=1317233025014-6841234.post@n2.nabble.com \
    --to=bus_nabble_git@semitwist.com \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).