On Mon, 2016-02-29 at 14:52 +, Emmanuele Bassi wrote:
> $ git pull github-mirror pull/${PR_ID}/head:pr-${PR_ID}
> $ git checkout pr-${PR_ID}
>
> From then on, you can push/merge/pull/rebase as usual.
Hi,
well, it's too much overhead for:
a) someone whom does not have a github
On Mon, 2016-02-29 at 15:44 +0100, Frederic Crozat wrote:
> Once you have the url of the pull request, just add ".patch" to it
> and you'll get a properly formatted patch.
Hi,
yes, that's the trick I was told to do. My point was that there is
absolutely no sign in the Web UI of github to
Hi;
On 29 February 2016 at 14:44, Frederic Crozat wrote:
> 2016-02-29 15:28 GMT+01:00 Milan Crha :
>
>> As I work with raw patches usually (I just got use to it after all the
>> years) the github web UI is very confusing for me and I didn't find a
>> way to
2016-02-29 15:28 GMT+01:00 Milan Crha :
> As I work with raw patches usually (I just got use to it after all the
> years) the github web UI is very confusing for me and I didn't find a
> way to convert the pull request into the patch. I asked a co-worker
> whom has a github
On Fri, 2016-02-26 at 23:30 +, Alberto Ruiz wrote:
> These contributions (there's about 200 pull requests, see link below)
> would likely not have happened if we didn't have a presence in
> Github. Shutting down the mirror would simply stop that energy.
Hi,
I think it would be good to
I actually was thinking about putting the intermediate build state
inside `$XDG_CACHE_HOME/jhbuild/build` by default, like we put the
downloaded tarballs in `$XDG_CACHE_HOME/jhbuild/downloads` by default.
I can check if `$HOME/jhbuild` exists, and put a `build` directory under there.
Ciao,
A big +1 to this idea.
As a nitpick, change the buildroot to '~/jhbuild/build'
because we use by default '~/jhbuild/checkout' and
'~/jhbuild/install', or convince jhbuild devs to change
default to '~/gnome/*'.
Cheers,
Carlos Soriano
- Original Message -
| Hi all;
|
| as you may know,