On Tue, Jan 24, 2012 at 5:00 PM, Bart Trojanowski wrote:
> On Tue, Jan 24, 2012 at 13:32, Aidan Van Dyk wrote:
>>
>> > does that sound about right? and is there a single command that
>> > would show all of that new content? thanks.
>>
>> I think the easiest way would be to pack everything befo
On Tue, Jan 24, 2012 at 13:32, Aidan Van Dyk wrote:
> > does that sound about right? and is there a single command that
> > would show all of that new content? thanks.
>
> I think the easiest way would be to pack everything before you start,
> and then after your commit, just look at all the l
On Tue, Jan 24, 2012 at 11:20 AM, Robert P. J. Day
wrote:
>
> in order to demonstrate what happens in the .git directory for a
> single commit, i'd like the simplest way to list all of the new
> objects that were added to the .git directory given changing a single
> file and committing that chang
in order to demonstrate what happens in the .git directory for a
single commit, i'd like the simplest way to list all of the new
objects that were added to the .git directory given changing a single
file and committing that change.
for example, let's say i've checked out the kernel source tre
