From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] [PATCH] Use the list class from the C++ STL, rather than C list macros.
Date: Thu, 30 Jan 2014 08:13:34 -0800 [thread overview]
Message-ID: <87eh3pla6p.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140130155914.GC6131@toaster.adamthompson.me.uk> (Adam Thompson's message of "Thu, 30 Jan 2014 15:59:14 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> Looks ok from an initial review, not built or tested though. Is this pushed?
No, it isn't pushed.
I wanted people to have a look before it is pushed.
> Also, how do I tell my repo to track the master repo now rather than my fork?
git remote set-url origin https://github.com/CMB/edbrowse.git
git remote set-url origin 'git@github.com:CMB/edbrowse.git
should do the trick.
If the master branch in your local repo is out of sync with the one on
CMB/edbrowse.git, you may also need to do something like:
git branch -D master
git branch master origin/master
git checkout master
But hopefully not.
git can be daunting. I still find it so at times, even though I've
been using it for about 6 years.
-- Chris
prev parent reply other threads:[~2014-01-30 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 15:14 Christopher Brannon
2014-01-30 15:59 ` Adam Thompson
2014-01-30 16:13 ` Chris Brannon [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=87eh3pla6p.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.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).