git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Frederik Dohr" <f.n.dohr@gmail.com>
To: git@vger.kernel.org
Cc: "Nico -telmich- Schottelius" <nico-git-svn-20080616@schottelius.org>
Subject: Re: git-svn breaks svn when adding .svn
Date: Mon, 16 Jun 2008 17:09:35 +0100	[thread overview]
Message-ID: <af6c748e0806160909t1e6dd22exf8e6d6c47215ec80@mail.gmail.com> (raw)
In-Reply-To: <200806161603.05166.thomas@koch.ro>

> I've reported the exact same problem on 18.04.08 under the subject: "git svn
> should refuse to checkin .svn directories"

Sorry about that - I did search the archives before having this
posted, but that didn't come up with anything (the search
functionality is quite limited though).

>> [...] Add this as the
>> pre-commit hook in .git/hooks (make sure to make it executable).

Not a bad idea - but this still requires manual intervention (and thus
awareness), which doesn't solve the potential destructiveness of this
issue.

> The Git website seems to be currently down, but one of us should search, if
> there is a Bugtracker for GIT and then open an issue for this.

The website is up again.
However, there doesn't seem to be a dedicated bug tracking tool.


-- F.

      parent reply	other threads:[~2008-06-16 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 12:24 How to compare different files in different branches Nico -telmich- Schottelius
2008-06-06 12:30 ` Jonathan del Strother
2008-06-06 12:34 ` Jakub Narebski
2008-06-06 12:38   ` Jakub Narebski
2008-06-06 12:35 ` Teemu Likonen
2008-06-08  9:47   ` Nico -telmich- Schottelius
2008-06-08  9:51     ` Junio C Hamano
2008-06-15  1:49       ` Ask Bjørn Hansen
2008-06-16 12:21       ` git-svn breaks svn when adding .svn Nico -telmich- Schottelius
     [not found]         ` <200806161603.05166.thomas@koch.ro>
2008-06-16 16:09           ` Frederik Dohr [this message]

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=af6c748e0806160909t1e6dd22exf8e6d6c47215ec80@mail.gmail.com \
    --to=f.n.dohr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nico-git-svn-20080616@schottelius.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).