public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Jason Merrill <jason@redhat.com>
Cc: Gabriel Dos Reis <dosreis@gmail.com>,
	 bkoz@redhat.com,	  gcc-patches@gcc.gnu.org
Subject: Re: git repository for constexpr
Date: Wed, 12 May 2010 13:42:00 -0000	[thread overview]
Message-ID: <87iq6tme5q.fsf@gauss.cs.tamu.edu> (raw)
In-Reply-To: <4BE37770.2030809@redhat.com> (Jason Merrill's message of "Thu\, 06 May 2010 22\:14\:08 -0400")

Jason Merrill <jason@redhat.com> writes:

| I've set up a git repository for constexpr work: the web interface is at
| 
|   http://repo.or.cz/w/official-gcc/constexpr.git
| 
| There are currently two branches there: master and jason.  The former
| contains a revision history based on the various patches you sent me,
| rebased onto recent trunk.  I figure that will track any reasonably
| complete changes.

Thanks for setting the repo to track this.

| jason is currently equivalent, but is intended to track my local
| constexpr working tree and might have changes that break things.
| 
| Starting from a git working tree as described in
|  http://gcc.gnu.org/wiki/GitMirror
| you can set up to use the constexpr repository as follows:
| 
| # git remote add cx git://repo.or.cz/official-gcc/constexpr.git
| # git remote set-url --push cx
| ssh://repo.or.cz/srv/git/official-gcc/constexpr.git
| # git config remote.cx.push constexpr:$MYNAME
| # git checkout -b constexpr cx/master
| 
| Of course, to push you'll need to create a repo.or.cz account and add
| yourself to the list of users.

OK.

| 
| To update from changes in the master branch, just 'git pull'.  To
| bring in changes from my branch as well, use 'git pull cx jason'.  To
| publish your changes to the $MYNAME branch, use 'git push'.  To update
| the master branch, use 'git push cx HEAD:master' (or some other
| refspec instead of HEAD).
| 
| Does this seem useful?

Yes, it does.  Many thanks.

| Do you have any local changes since the last patch you sent me?

Yes, I'll send them to the list as well as pushing into the repo.
Does that sound right, or is that unnecessary noise -- as a general
question about how we handle changes to the repo?

Again, thanks!

-- Gaby

  reply	other threads:[~2010-05-12 13:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  1:42 C++ PATCH " Gabriel Dos Reis
2009-11-29 10:35 ` Jason Merrill
2009-11-29 19:11   ` Gabriel Dos Reis
2009-11-30  6:37     ` Jason Merrill
2009-11-30  8:18       ` Gabriel Dos Reis
2009-11-30 20:21         ` Jason Merrill
2009-12-01  0:24           ` Gabriel Dos Reis
2009-12-01  0:32           ` Gabriel Dos Reis
2009-12-02 23:10             ` Jason Merrill
2009-12-02 23:11               ` Gabriel Dos Reis
2009-12-04  1:31                 ` [C++] constexpr testsuite Benjamin Kosnik
2009-12-13 19:56                   ` Gabriel Dos Reis
2009-12-13 22:25                     ` Dave Korn
2009-12-14 10:27                       ` Gabriel Dos Reis
2009-12-14  7:29                     ` Benjamin Kosnik
2009-12-07 16:21                 ` C++ PATCH for constexpr Jason Merrill
2010-01-06 16:17                 ` Jason Merrill
2010-01-12  2:18                   ` Benjamin Kosnik
2010-02-02 18:25                   ` Jason Merrill
2010-02-02 18:29                     ` Gabriel Dos Reis
2010-02-02 18:33                       ` Paolo Carlini
2010-02-02 18:37                         ` Gabriel Dos Reis
2010-02-03  3:48                         ` Dave Korn
2010-02-02 18:56                       ` Jason Merrill
2010-02-02 19:24                         ` Gabriel Dos Reis
2010-05-07  2:14                           ` git repository for constexpr (was Re: C++ PATCH for constexpr) Jason Merrill
2010-05-12 13:42                             ` Gabriel Dos Reis [this message]
2010-05-12 15:27                               ` git repository for constexpr Jason Merrill
2010-06-02 20:30                                 ` Jason Merrill
2010-07-14 17:36                             ` git repository for constexpr (was Re: C++ PATCH for constexpr) Jason Merrill
2010-07-15  1:02                               ` constexpr for zurich! let's make it happen Benjamin Kosnik
2010-07-16 14:03                               ` git repository for constexpr (was Re: C++ PATCH for constexpr) Jason Merrill
2009-11-29 16:24 ` C++ PATCH for constexpr Jason Merrill
2009-11-29 17:32   ` Gabriel Dos Reis

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=87iq6tme5q.fsf@gauss.cs.tamu.edu \
    --to=gdr@cs.tamu.edu \
    --cc=bkoz@redhat.com \
    --cc=dosreis@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).