On Fri, Aug 2, 2019 at 9:32 PM Junio C Hamano wrote:
>
> Piotr Krukowiecki writes:
>
> > At this moment I'm not sure myself if I consider this a bug or not.
>
> This definitely is not a bug but is a designed and intended
> behaviour.
(generally speaking)
By "bug" I mean wrong behaviour. Designs
Piotr Krukowiecki writes:
> At this moment I'm not sure myself if I consider this a bug or not.
This definitely is not a bug but is a designed and intended
behaviour.
Think of running "git log" without "--full-history" that is limited
with a pathspec as a tool to ask Git to show _one_ way (pref
On Fri, Aug 2, 2019 at 4:22 PM Derrick Stolee wrote:
>
> On 8/2/2019 5:38 AM, Piotr Krukowiecki wrote:
> > Hi,
> >
> > I have merged a branch into master.
> >
> > When on master I do "git log -- some/file", it does not show commits
> > from merged branch (which I know they changed the file).
> > I
On 8/2/2019 5:38 AM, Piotr Krukowiecki wrote:
> Hi,
>
> I have merged a branch into master.
>
> When on master I do "git log -- some/file", it does not show commits
> from merged branch (which I know they changed the file).
> I have to add "--full-history" to see the commits.
> When I run "git lo
Hi,
I have merged a branch into master.
When on master I do "git log -- some/file", it does not show commits
from merged branch (which I know they changed the file).
I have to add "--full-history" to see the commits.
When I run "git log" (without "-- some/file") I can see the commits
without usin
5 matches
Mail list logo