On Wed, May 25, 2016 at 12:17:18PM +0200, Christian Heimes wrote:
>
> I don't know why github either forces merge commits or a single squashed
> commit. If I would have to guess, I would assume it has philosophical
> reasons. It took many years to get github to add an alternative to merge
The
On 05/25/2016 11:55 AM, Christian Heimes wrote:
> On 2016-05-25 11:46, Martin Kosek wrote:
>> On 05/25/2016 10:03 AM, Jan Pazdziora wrote:
>>> On Mon, May 23, 2016 at 04:24:38PM +0200, Florence Blanc-Renaud wrote:
- I start working on a specific issue and decide to create a branch on my
On 2016-05-25 11:46, Martin Kosek wrote:
> On 05/25/2016 10:03 AM, Jan Pazdziora wrote:
>> On Mon, May 23, 2016 at 04:24:38PM +0200, Florence Blanc-Renaud wrote:
>>>
>>> - I start working on a specific issue and decide to create a branch on my
>>> git repository (on my laptop)
>>> git clone
On 05/25/2016 10:03 AM, Jan Pazdziora wrote:
> On Mon, May 23, 2016 at 04:24:38PM +0200, Florence Blanc-Renaud wrote:
>>
>> - I start working on a specific issue and decide to create a branch on my
>> git repository (on my laptop)
>> git clone git://git.fedorahosted.org/git/freeipa.git
>> git
On Mon, May 23, 2016 at 04:33:29PM +0200, Martin Basti wrote:
>
>
> On 23.05.2016 16:24, Florence Blanc-Renaud wrote:
> > Hi all,
> >
> > as I am ramping up with git, I have a few questions. Let's imagine the
> > following development workflow:
> >
> > - I start working on a specific issue and
On 23.05.2016 16:24, Florence Blanc-Renaud wrote:
Hi all,
as I am ramping up with git, I have a few questions. Let's imagine the
following development workflow:
- I start working on a specific issue and decide to create a branch on
my git repository (on my laptop)
git clone
