8:39 p.m.
I'm trying to find the changes associated with this issue:
https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
I can't seem to find a way to search the jboss-as git commits. Am I
missing a search box somewhere? The only one I can find up in the corner
appears to want to search repo names or something not useful.
Is there any way to tie this workflow info to the commit?
Project JBoss Application Server[ 10030 ] Application Server 7[
12311211 ]
Key JBAS-9270 AS7-486 <https://issues.jboss.org/browse/AS7-486>
Workflow jira[ 12444066 ] GIT Pull Request workflow[ 12447354 ]
Component/s
CLI[ 12313802 ]
Component/s CLI[ 12313755 ]
Fix Version/s
7.0.0.Beta3[ 12316375 ]
9:04 p.m.
On 05/18/2011 01:39 PM, Scott Stark wrote:
I'm trying to find the changes associated with this issue:
https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
I can't seem to find a way to search the jboss-as git commits. Am I
missing a search box somewhere? The only one I can find up in the corner
appears to want to search repo names or something not useful.
Is there any way to tie this workflow info to the commit?
I've always just done "git log | grep -i whatever" or browsed the log
via the default pager. It's fast enough that even searching the whole
history is pretty quick.
--
- DML
1:34 a.m.
Curious. Ok, I can get that to do what I need, but I'm surprised that
log will not take a commit id. The git log --help output was amazing
long, but I could not see how to request a specific commit.
On 5/18/11 12:04 PM, David M. Lloyd wrote:
On 05/18/2011 01:39 PM, Scott Stark wrote:
> I'm trying to find the changes associated with this issue:
>
> https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
> I can't seem to find a way to search the jboss-as git commits. Am I
> missing a search box somewhere? The only one I can find up in the corner
> appears to want to search repo names or something not useful.
>
> Is there any way to tie this workflow info to the commit?
I've always just done "git log | grep -i whatever" or browsed the log
via the default pager. It's fast enough that even searching the whole
history is pretty quick.
1:46 a.m.
That's just:
git log 01234567...
where 01234567... is the commit ID. If nothing comes back, you don't
have it.
On 05/18/2011 06:34 PM, Scott Stark wrote:
Curious. Ok, I can get that to do what I need, but I'm surprised
that
log will not take a commit id. The git log --help output was amazing
long, but I could not see how to request a specific commit.
On 5/18/11 12:04 PM, David M. Lloyd wrote:
> On 05/18/2011 01:39 PM, Scott Stark wrote:
>> I'm trying to find the changes associated with this issue:
>>
>> https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
>> I can't seem to find a way to search the jboss-as git commits. Am I
>> missing a search box somewhere? The only one I can find up in the corner
>> appears to want to search repo names or something not useful.
>>
>> Is there any way to tie this workflow info to the commit?
> I've always just done "git log | grep -i whatever" or browsed the log
> via the default pager. It's fast enough that even searching the whole
> history is pretty quick.
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
2:02 a.m.
Ok, that works, but I still don't see how that syntax is described in
the log help output. It is showing much more than just that commit. For
example, I found a commit using:
[130](ironmaiden:jboss-as) > git log | grep -C 4 JBAS-9270
commit f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 18:00:19 2011 +0200
JBAS-9270
commit 3ba68df3485f48f285f28dedf46dee077529b835
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 16:58:03 2011 +0200
JBAS-9270
commit 504042983d2e8f71b271c81b7b1c5640cceded0f
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 12:24:27 2011 +0200
Now I do git log f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
[133](ironmaiden:jboss-as) > git log
f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
commit f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 18:00:19 2011 +0200
JBAS-9270
commit 3ba68df3485f48f285f28dedf46dee077529b835
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 16:58:03 2011 +0200
JBAS-9270
commit 504042983d2e8f71b271c81b7b1c5640cceded0f
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Fri Apr 8 12:24:27 2011 +0200
JBAS-9238
commit 6a287a7c74568e8393568350d72490d91fcb30bc
Author: Alexey Loubyansky <olubyans(a)tstudio.(none)>
Date: Thu Apr 7 22:59:13 2011 +0200
JBAS-9269, JBAS-9271
....page after page of log command output...
On 5/18/11 4:46 PM, David M. Lloyd wrote:
That's just:
git log 01234567...
where 01234567... is the commit ID. If nothing comes back, you don't
have it.
On 05/18/2011 06:34 PM, Scott Stark wrote:
> Curious. Ok, I can get that to do what I need, but I'm surprised that
> log will not take a commit id. The git log --help output was amazing
> long, but I could not see how to request a specific commit.
>
> On 5/18/11 12:04 PM, David M. Lloyd wrote:
>> On 05/18/2011 01:39 PM, Scott Stark wrote:
>>> I'm trying to find the changes associated with this issue:
>>>
>>> https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
>>> I can't seem to find a way to search the jboss-as git commits. Am I
>>> missing a search box somewhere? The only one I can find up in the corner
>>> appears to want to search repo names or something not useful.
>>>
>>> Is there any way to tie this workflow info to the commit?
>> I've always just done "git log | grep -i whatever" or browsed the
log
>> via the default pager. It's fast enough that even searching the whole
>> history is pretty quick.
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:15 a.m.
Well a git commit is the culmination of a change plus the commit that
came before it. So, if you ask for the log of a specific rev, you get
what it is in full. If you want information about just one change, then
"git show f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42" might help.
On 05/18/2011 07:02 PM, Scott Stark wrote:
Ok, that works, but I still don't see how that syntax is
described in
the log help output. It is showing much more than just that commit. For
example, I found a commit using:
[130](ironmaiden:jboss-as)> git log | grep -C 4 JBAS-9270
commit f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 18:00:19 2011 +0200
JBAS-9270
commit 3ba68df3485f48f285f28dedf46dee077529b835
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 16:58:03 2011 +0200
JBAS-9270
commit 504042983d2e8f71b271c81b7b1c5640cceded0f
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 12:24:27 2011 +0200
Now I do git log f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
[133](ironmaiden:jboss-as)> git log
f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
commit f8f5e98f0db9de0d225ef96a9a88dec3e5b84a42
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 18:00:19 2011 +0200
JBAS-9270
commit 3ba68df3485f48f285f28dedf46dee077529b835
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 16:58:03 2011 +0200
JBAS-9270
commit 504042983d2e8f71b271c81b7b1c5640cceded0f
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Fri Apr 8 12:24:27 2011 +0200
JBAS-9238
commit 6a287a7c74568e8393568350d72490d91fcb30bc
Author: Alexey Loubyansky<olubyans(a)tstudio.(none)>
Date: Thu Apr 7 22:59:13 2011 +0200
JBAS-9269, JBAS-9271
....page after page of log command output...
On 5/18/11 4:46 PM, David M. Lloyd wrote:
> That's just:
>
> git log 01234567...
>
> where 01234567... is the commit ID. If nothing comes back, you don't
> have it.
>
> On 05/18/2011 06:34 PM, Scott Stark wrote:
>> Curious. Ok, I can get that to do what I need, but I'm surprised that
>> log will not take a commit id. The git log --help output was amazing
>> long, but I could not see how to request a specific commit.
>>
>> On 5/18/11 12:04 PM, David M. Lloyd wrote:
>>> On 05/18/2011 01:39 PM, Scott Stark wrote:
>>>> I'm trying to find the changes associated with this issue:
>>>>
>>>> https://issues.jboss.org/browse/AS7-486 formerly known as JBAS-9270, but
>>>> I can't seem to find a way to search the jboss-as git commits. Am I
>>>> missing a search box somewhere? The only one I can find up in the corner
>>>> appears to want to search repo names or something not useful.
>>>>
>>>> Is there any way to tie this workflow info to the commit?
>>> I've always just done "git log | grep -i whatever" or browsed
the log
>>> via the default pager. It's fast enough that even searching the whole
>>> history is pretty quick.
>>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
4726
days inactive
4727
days old
6 comments
2 participants
participants (2)
-
David M. Lloyd -
Scott Stark