git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Ethan Clevenger <ethan@sternerstuffdesign.com>
Cc: git@vger.kernel.org, Hiroshi Shirosaki <h.shirosaki@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: Bug? git svn tag Authentication failed
Date: Thu, 4 May 2017 16:37:16 +0000	[thread overview]
Message-ID: <20170504163716.GA20370@starla> (raw)
In-Reply-To: <CAOY55trVg7CYqzp7vTxaeVnqvM7YKnys-+88DnDRc4nbmBEBAg@mail.gmail.com>

Ethan Clevenger <ethan@sternerstuffdesign.com> wrote:
> Git version: 2.12.2.windows.2
> 
> `git svn tag 1.0` results in:

<snip>

Note, "git svn tag" uses the same backend code as "git svn branch",
and there was a recent fix for that in
commit e0688e9b28f2c5ff711460ee8b62077be5df2360
("git svn: fix authentication with 'branch'")

Looks like that change will be in 2.13 (it's in all the
release-canditates), but it should backported to 2.12.x

Junio: I think that commit should go into 'maint', too.  Thanks.

> In my .subversion directory I do have cached credentials under
> auth/svn.simple. A vanilla svn CLI commit also works:
> 
> >  svn ci -m 'do creds work?'
> > Adding         trunk\.bar
> > Transmitting file data .done
> > Committing transaction...
> > Committed revision 1651133.
> 
> 
> Unsure if this is actually a bug or my oversight.

Seems like a bug to me.  Can you try one of the 2.13 release
candidates to confirm?  Thanks.

      reply	other threads:[~2017-05-04 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 16:21 Bug? git svn tag Authentication failed Ethan Clevenger
2017-05-04 16:37 ` Eric Wong [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=20170504163716.GA20370@starla \
    --to=e@80x24.org \
    --cc=ethan@sternerstuffdesign.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=h.shirosaki@gmail.com \
    /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).