Hey,
The new version of git-review released today (1.22) includes a patch I
wrote that makes it possible to work against a single 'origin' remote. This
amounts to a workaround for git-review's tendency to frighten you into
thinking you're about to submit more patches than the ones you are working
On Fri, May 31, 2013 at 6:14 PM, Ori Livneh wrote:
> The new version of git-review released today (1.22) includes a patch I
> wrote that makes it possible to work against a single 'origin' remote. This
> amounts to a workaround for git-review's tendency to frighten you into
> thinking you're about
On 05/31/2013 06:14 PM, Ori Livneh wrote:
> Hey,
>
> The new version of git-review released today (1.22) includes a patch I
> wrote that makes it possible to work against a single 'origin' remote.
Cool, thank you.
Matt Flaschen
___
Wikitech-l mailing
> Hey,
>
> The new version of git-review released today (1.22) includes a patch I
> wrote that makes it possible to work against a single 'origin' remote.
I just want to point out that both Ori and Krenair contributed to this
release of git-review (a couple patches each):
https://review.openstac
Hey,
Did you add this useful documentation on meta? If yes, please provide me
the link so I can add this to my "toread/todo" list.
Le vendredi 31 mai 2013 à 15:14 -0700, Ori Livneh a écrit :
> Hey,
>
> The new version of git-review released today (1.22) includes a patch I
> wrote that makes it
On Sat, Jun 1, 2013 at 12:14 AM, Ori Livneh wrote:
> This
> amounts to a workaround for git-review's tendency to frighten you into
> thinking you're about to submit more patches than the ones you are working
> on.
>
Thanks Ori, I have tested it with a couple of repositories and it works
great. N
Thank you!
On 05/31/2013 03:14 PM, Ori Livneh wrote:
Hey,
The new version of git-review released today (1.22) includes a patch I
wrote that makes it possible to work against a single 'origin' remote. This
amounts to a workaround for git-review's tendency to frighten you into
thinking you're ab
I wonder if "origin" should be made the default setting for gerrit - after
all every new git clone automatically uses "origin". The fewer "surprise!"
moments devs have, the more productive we become.
On Wed, Jun 5, 2013 at 6:42 PM, Juliusz Gonera wrote:
> Thank you!
>
>
>
> On 05/31/2013 03:14 P
Tried setting up the global config in /etc. git-review's gone wild with an
exception (very sorry, I switched the terminal off and cannot provide the
backtrace; I remember it wanted 'updates' section or some kind of). Luckly
~/.config/ worked well, thanks!
On Sat, Jun 1, 2013 at 1:14 AM, Ori Livne
Not if they fork from our github mirror and their origin is their own repo.
Personally my origin is the github remote I push my unfinished branches of
code too. I use 'core' for the actual gerrit remote.
And I didn't even fork. I did this before we had a github mirror.
--
~Daniel Friesen (Dan
Daniel, I am not saying it will solve everyone's usage scenarios, but I
think one would agree that for the majority of the developers, "origin" is
set by default. Even gerrit's own usage of "navigate to gerrit.wikimedia.org,
and copy "git clone" command from the project page" uses "origin", not "-o
I agree it would be nice for our repos (or git-review setup steps) would have
sane defaults instead of ones almost everyone will want to change to not be
annoyed.
--
View this message in context:
http://wikimedia.7.x6.nabble.com/New-git-review-lets-you-configure-origin-as-the-gerrit-remote-tp50
On Thu, Jun 6, 2013 at 12:37 AM, Aaron Schulz wrote:
> I agree it would be nice for our repos (or git-review setup steps) would
> have
> sane defaults instead of ones almost everyone will want to change to not be
> annoyed.
Setting defaultremote=origin in each repository's .gitreview file would
Le 06/06/13 00:45, Yuri Astrakhan a écrit :
> I wonder if "origin" should be made the default setting for gerrit - after
> all every new git clone automatically uses "origin". The fewer "surprise!"
> moments devs have, the more productive we become.
This is how I name my git remotes:
For Gerrit b
This is great! Origin and gerrit remotes disagreeing could potentially
cause havoc. saper and I went through some tutorials telling people to use
`git clone -o gerrit` when starting development, but this is much cleaner.
I added it to
https://www.mediawiki.org/wiki/Gerrit/Tutorial#Prepare_to_work_
This was working great for me on several machines, but it did not work on
one machine[1][2].
Adding something like this to git-review.conf fixes the problem:
[updates]
check=off
Željko
--
1: https://bugzilla.wikimedia.org/show_bug.cgi?id=55732
2: https://bugs.launchpad.net/git-review/+bug/124304
16 matches
Mail list logo