From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: Questions on package adoption conventions
Date: Wed, 04 Nov 2015 11:36:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.63.1511040319290.44260@m0.truegem.net> (raw)
In-Reply-To: <20151102092901.GW5319@calimero.vinschen.de>
I was able to 'git clone' the cygutils source tree and fix user-reported
issues and my build issues. I'm ready to push the updates but have hit a
snag...
--------8<--------
<prompt> git push origin master
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
-------->8--------
I tried creating a git branch and pushing that instead; same error.
Adding -v to the 'git push' command shows "Pushing to
git://sourceware.org/git/cygwin-cygutils.git" which seems correct.
I suspect my login credentials are incorrect. How/where do I specify what
my sourceware login is? Or maybe it's some other problem?
Separate from that, I will need to update the cygutils.cygport file which
resides outside of this cygutils source tree. How do I access that file?
And if that wasn't enough, here's another newbie question: Am I really
supposed to push to master or is there a review that should be done first?
So pushing a revision branch is the right way to allow for a review?
Thanks for any hints,
..mark
next prev parent reply other threads:[~2015-11-04 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 21:48 Mark Geisert
2015-10-30 22:07 ` Marco Atzeri
2015-10-30 23:25 ` Mark Geisert
2015-10-30 23:59 ` Marco Atzeri
2015-10-31 0:18 ` Jon Turney
2015-10-31 16:03 ` Corinna Vinschen
2015-11-01 4:15 ` Mark Geisert
2015-11-02 9:29 ` Corinna Vinschen
2015-11-04 11:36 ` Mark Geisert [this message]
2015-11-04 12:08 ` Corinna Vinschen
2015-11-04 18:48 ` Achim Gratz
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=Pine.BSF.4.63.1511040319290.44260@m0.truegem.net \
--to=mark@maxrnd.com \
--cc=cygwin-apps@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).