[LU-5643] Flubbed merging of two patches in change I1d69b64eec1589f63e24f20cc624778a4be2ec60 Created: 19/Sep/14 Updated: 29/Oct/14 Resolved: 29/Oct/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.3 |
| Fix Version/s: | Lustre 2.5.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Christopher Morrone | Assignee: | Nathaniel Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||
| Severity: | 3 | ||||||||||||||||||||
| Rank (Obsolete): | 15815 | ||||||||||||||||||||
| Description |
|
I think that change http://review.whamcloud.com/#/c/11297/ is a good example of why you guys need to stop merging multiple commits into one. This is really truly a horrible way to go about doing things. Here are two reasons: 1) The subject of the patch comes from only one of the tickets and patches, so when I do "git log --oneline" or look at the tree in gitk or any any number of other tools, it is not even the slightest bit obvious that this isn't the same patch from master, but a combination of two patches. Bad, bad, bad. Long story short, |
| Comments |
| Comment by Peter Jones [ 20/Sep/14 ] |
|
Nathaniel Could you please check with some additional changes are needed on b2_5? Thanks Peter |
| Comment by Nathaniel Clark [ 22/Sep/14 ] |
| Comment by Nathaniel Clark [ 29/Oct/14 ] |
|
Patch landed to b2_5 (Oct 1. 2014) |