commits" which in Perforce are represented by concept of pending
changelists.
On Thu, Jul 13, 2017 at 2:22 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> On Tue, Jul 11, 2017 at 8:45 AM, Nikolay Shustov
>>
>>> With Git I cannot seem to finding the possibility to
g. revert file2 will remove it from changelist A)
How would I do it with sets of files that would belong to Git commit?
On Thu, Jul 13, 2017 at 2:09 PM, Junio C Hamano wrote:
> Nikolay Shustov writes:
>
>> Thank you for the detailed explanation, it looks like merging the
>> co
hat I need.
On Tue, Jul 11, 2017 at 6:27 PM, astian wrote:
> Nikolay Shustov wrote:
>> With Perforce, I can have multiple changelists opened, that group the
>> changed files as needed.
>>
>> With Git I cannot seem to finding the possibility to figure out how to
>
to correct me if I miss something.
>
> On 11/07/2017 19:39, Lars Schneider wrote:
>>
>>> On 11 Jul 2017, at 17:45, Nikolay Shustov wrote:
>>>
>>> Hi,
>>> I have been recently struggling with migrating my development workflow
>>> from Perforce to Git
Lars Schneider
wrote:
>> On Tue, Jul 11, 2017 at 1:39 PM, Lars Schneider
>> wrote:
>>>
>>>> On 11 Jul 2017, at 17:45, Nikolay Shustov
>>>> wrote:
>>>>
>>>> Hi,
>>>> I have been recently struggling with migrating my deve
; On Tue, Jul 11, 2017 at 11:10 AM, Nikolay Shustov
> wrote:
>> Thank you for the explanation. The example about backend and frontend
>> is relevant even though I normally have to deal with more layers at
>> the same time.
>>
>> However, in my case I have the t
y with the certain attribute
You've kindly demonstrated that #4 is doable; however I could not
clearly get for the Git documentation if #1 - #3 are achievable...
Could you point me to the right place in the documentation, please?
On Tue, Jul 11, 2017 at 1:27 PM, Junio C Hamano wrote:
&g
ely
every change for feature A and for feature B would probably a good
option unless I have many changes and then cherry-picking the proper
commits to create a single changeset for the integration would become
a nightmare.
On Tue, Jul 11, 2017 at 1:39 PM, Lars Schneider
wrote:
>
>> On 11 Jul 20
"build/test" code tree. Plus merging the changes from one to another.
A bit too much, IMHO.
On Tue, Jul 11, 2017 at 1:18 PM, Stefan Beller wrote:
> On Tue, Jul 11, 2017 at 8:45 AM, Nikolay Shustov
> wrote:
>> Hi,
>> I have been recently struggling with migrating my
Hi,
I have been recently struggling with migrating my development workflow
from Perforce to Git, all because of the following thing:
I have to work on several features in the same code tree parallel, in
the same Perforce workspace. The major reason why I cannot work on one
feature then on another
10 matches
Mail list logo
