You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by Eli Reisman <ap...@gmail.com> on 2013/03/28 23:16:41 UTC
our git repo
Hey folks,
I notice on the branches of our git repo, we have a bunch of wierd temp
branches again (were those commits meant for trunk? did they get into
trunk?) and we are now missing or 0.1 release branch.
Is all this intentional? Whats the deal with the new branches?
Thanks,
Eli
Re: our git repo
Posted by Eli Reisman <ap...@gmail.com>.
I'll check again, didn't see one that night, there was a 0.1 branch before
that showed up with git branch -a
On Mon, Apr 1, 2013 at 6:25 PM, Nitay <ni...@gmail.com> wrote:
> I think there is a tag for it.
>
>
> On Mon, Apr 1, 2013 at 9:14 AM, Avery Ching <ac...@apache.org> wrote:
>
> > Isn't there a branch-0.1? I see it in my git.
> >
> >
> > On 3/29/13 5:29 PM, Eli Reisman wrote:
> >
> >> Avery, you know where our 0.1 release branch went to?
> >>
> >>
> >> On Thu, Mar 28, 2013 at 11:18 PM, Avery Ching <ac...@apache.org>
> wrote:
> >>
> >> So the tricky part is that you have to be careful about how you push to
> >>> our git repo, or else you create a new remote branch automatically.
> >>>
> >>> Here's how I do it.
> >>>
> >>> git push origin <local branch name>:trunk
> >>>
> >>> I'm sure there are other ways, but if you forget ":trunk", hello new
> >>> branch!
> >>>
> >>> Avery
> >>>
> >>>
> >>> On 3/28/13 3:16 PM, Eli Reisman wrote:
> >>>
> >>> Hey folks,
> >>>>
> >>>> I notice on the branches of our git repo, we have a bunch of wierd
> temp
> >>>> branches again (were those commits meant for trunk? did they get into
> >>>> trunk?) and we are now missing or 0.1 release branch.
> >>>>
> >>>> Is all this intentional? Whats the deal with the new branches?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Eli
> >>>>
> >>>>
> >>>>
> >
>
Re: our git repo
Posted by Nitay <ni...@gmail.com>.
I think there is a tag for it.
On Mon, Apr 1, 2013 at 9:14 AM, Avery Ching <ac...@apache.org> wrote:
> Isn't there a branch-0.1? I see it in my git.
>
>
> On 3/29/13 5:29 PM, Eli Reisman wrote:
>
>> Avery, you know where our 0.1 release branch went to?
>>
>>
>> On Thu, Mar 28, 2013 at 11:18 PM, Avery Ching <ac...@apache.org> wrote:
>>
>> So the tricky part is that you have to be careful about how you push to
>>> our git repo, or else you create a new remote branch automatically.
>>>
>>> Here's how I do it.
>>>
>>> git push origin <local branch name>:trunk
>>>
>>> I'm sure there are other ways, but if you forget ":trunk", hello new
>>> branch!
>>>
>>> Avery
>>>
>>>
>>> On 3/28/13 3:16 PM, Eli Reisman wrote:
>>>
>>> Hey folks,
>>>>
>>>> I notice on the branches of our git repo, we have a bunch of wierd temp
>>>> branches again (were those commits meant for trunk? did they get into
>>>> trunk?) and we are now missing or 0.1 release branch.
>>>>
>>>> Is all this intentional? Whats the deal with the new branches?
>>>>
>>>> Thanks,
>>>>
>>>> Eli
>>>>
>>>>
>>>>
>
Re: our git repo
Posted by Avery Ching <ac...@apache.org>.
Isn't there a branch-0.1? I see it in my git.
On 3/29/13 5:29 PM, Eli Reisman wrote:
> Avery, you know where our 0.1 release branch went to?
>
>
> On Thu, Mar 28, 2013 at 11:18 PM, Avery Ching <ac...@apache.org> wrote:
>
>> So the tricky part is that you have to be careful about how you push to
>> our git repo, or else you create a new remote branch automatically.
>>
>> Here's how I do it.
>>
>> git push origin <local branch name>:trunk
>>
>> I'm sure there are other ways, but if you forget ":trunk", hello new
>> branch!
>>
>> Avery
>>
>>
>> On 3/28/13 3:16 PM, Eli Reisman wrote:
>>
>>> Hey folks,
>>>
>>> I notice on the branches of our git repo, we have a bunch of wierd temp
>>> branches again (were those commits meant for trunk? did they get into
>>> trunk?) and we are now missing or 0.1 release branch.
>>>
>>> Is all this intentional? Whats the deal with the new branches?
>>>
>>> Thanks,
>>>
>>> Eli
>>>
>>>
Re: our git repo
Posted by Eli Reisman <ap...@gmail.com>.
Avery, you know where our 0.1 release branch went to?
On Thu, Mar 28, 2013 at 11:18 PM, Avery Ching <ac...@apache.org> wrote:
> So the tricky part is that you have to be careful about how you push to
> our git repo, or else you create a new remote branch automatically.
>
> Here's how I do it.
>
> git push origin <local branch name>:trunk
>
> I'm sure there are other ways, but if you forget ":trunk", hello new
> branch!
>
> Avery
>
>
> On 3/28/13 3:16 PM, Eli Reisman wrote:
>
>> Hey folks,
>>
>> I notice on the branches of our git repo, we have a bunch of wierd temp
>> branches again (were those commits meant for trunk? did they get into
>> trunk?) and we are now missing or 0.1 release branch.
>>
>> Is all this intentional? Whats the deal with the new branches?
>>
>> Thanks,
>>
>> Eli
>>
>>
>
Re: our git repo
Posted by Avery Ching <ac...@apache.org>.
So the tricky part is that you have to be careful about how you push to
our git repo, or else you create a new remote branch automatically.
Here's how I do it.
git push origin <local branch name>:trunk
I'm sure there are other ways, but if you forget ":trunk", hello new branch!
Avery
On 3/28/13 3:16 PM, Eli Reisman wrote:
> Hey folks,
>
> I notice on the branches of our git repo, we have a bunch of wierd temp
> branches again (were those commits meant for trunk? did they get into
> trunk?) and we are now missing or 0.1 release branch.
>
> Is all this intentional? Whats the deal with the new branches?
>
> Thanks,
>
> Eli
>