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]

Re: Avoid reuse of MIPS "hi" and "lo"


On Sat, Sep 26, 2009 at 11:44:13AM +0200, Andreas Schwab wrote:
> Just "git push" should work.  You can always check with --dry-run if you
> are unsure.

It didn't:

drow@caradoc:/space/fsf/commit/glibc-ports% git push --dry-run
warning: You did not specify any refspecs to push, and the current remote
warning: has not configured any push refspecs. The default action in this
warning: case is to push all matching refspecs, that is, all branches
warning: that exist both locally and remotely will be updated.  This may
warning: not necessarily be what you want to happen.
warning:
warning: You can specify what action you want to take in this case, and
warning: avoid seeing this message again, by configuring 'push.default' to:
warning:   'nothing'  : Do not push anything
warning:   'matching' : Push all matching branches (default)
warning:   'tracking' : Push the current branch to whatever it is tracking
warning:   'current'  : Push the current branch
fatal: The remote end hung up unexpectedly

The warning doesn't explain what caused the fatal error, though.  I
remember the same thing happenign with --dry-run.  Is this caused by
the git: vs ssh: distinction?

> There is nothing wrong with using the local tracking branch for simple
> development.

Thanks.

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]