This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tuesday 29 September 2009 20:16:07 Mike Frysinger wrote: > On Sunday 27 September 2009 10:12:36 Carlos O'Donell wrote: > > On Sat, Sep 26, 2009 at 5:44 AM, Andreas Schwab wrote: > > > Daniel Jacobowitz <drow@false.org> writes: > > >> I ended up with: > > >> > > >> git push ssh://sourceware.org/git/glibc-ports.git master:master > > > > > > Just "git push" should work. You can always check with --dry-run if > > > you are unsure. > > > > I've updated the wiki. For "git push" to work you have to checkout > > using ssh://, but the wiki doesn't say that. > > > > I've updated the wiki to mention the use of ssh://, using git push, > > and the need for you to use your sourceware ssh keys. > > this is incorrect, but not sure how much it really matters to people here. > the original clone URL has no bearing at all on where you push things. > personally, i always clone the public/anon interface and setup another > remote URL for pushing. oh, and you dont need to delete your git clone to simply change the original clone url. this is set in remote.origin.url, so do: git config remote.origin.url ssh://new/url/you/want/to/use -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |