search for: blame

This will be a git feature in git 2.23 (in Q3 2019). It will allow git blame to ignore revisions with --ignore-rev, which the user can even specify in their git config. Relevant git blame documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125 Relevant git config documentation change: https:/...

As a very frequent explorer of history, I really don't think this is as big an issue as it may seem. Even absent refactorings, you often run into the "wrong" commit when looking at blame (e.g., someone just added a comma rather than actually changing the code you care about), and have to look past that, to another previous commit. Any interactive blame tool ought to have an easy way to do this. For example, in emacs's annotation mode (which is what I use), you just press '...

Hello all, I broke the build, but I did not receive any blame email about it. I have a feeling the blame emails are not working. Is anyone experiencing the same thing? Could it be related to the last-week master restart (which seems to have reset build numbers as well)? regards, pl

...changes to agree to a timeline. How are we making sure everyone is aware and ready? Will we have something at the dev meeting? Some more questions: * Is it worth waiting until after the monorepo migration? * While we’re at it, should we clang-format everything? * How do we expect to maintain git blame history, if at all? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190722/10191bc5/attachment.html>

...entire LLVM repo including subprojects to the new naming scheme without breaking them. - Many projects, especially LLVM and Clang have lots of out-of-tree downstream repos. We need to provide a tool to rebase such repos to a commit after a renaming. - The sweeping change shouldn't break `git blame`. What I learned from the lld's naming scheme change: - There are many member variables in the LLVM/lld codebase that have the same name as accessors ignoring case (i.e. many classes define foo() as an accessor to a member variable Foo). Such variables would conflict with functions after ren...

Hi folks, Git is on its way to learning how to ignore commits, allowing us to do variable renaming and other small refactorings without breaking git blame. It's like git-hyper-blame [1] but significantly more powerful as it uses fuzzy matching to match lines, including lines that may have been split or joined. A preview release of Git with this new feature is at: https://github.com/mplatings/git/releases/tag/ignore-rev Some of you have told me...

...end. I would like to fix it. This will be a mechanical change just organizing code in a way that makes it easy and fast to find methods and related static helpers. It will not change any actual functionality. But it will pretty much completely break the utility of looking at only a single layer of blame. Fortunately we have nice tools like 'git blame' that can step incrementally back through time. If anyone is radically opposed to me cleaning up TargetLowering.h, TargetLoweringBase.cpp, and X86ISelLowering.{h,cpp}, shout. Otherwise, I will clean this up with a vengence. I've CC'ed...

...s. I have one for every day for this server. All of them had either the overwritten (ok, backup too new) or the version before they started to share. Now my question. Who is the suspect? Could it be that rsync just can't handle such files or that excel does some bullshit? I hope the later is to blame ;) Thanks in advance for help or hints! Regards, syncro -- View this message in context: http://www.nabble.com/Problem-with-shared-xls-file.-Could-it-be-blamed-on-rsync--tf3408546.html#a9495289 Sent from the Samba - rsync mailing list archive at Nabble.com.

...er-rt] Fix ptrace interceptor for aarch64'. ________________________________ From: Galina Kistanova [gkistanova at gmail.com] Sent: 02 November 2015 16:03 To: Daniel Sanders Cc: Renato Golin; Bill Seurer; LLVM Dev Subject: Re: [llvm-dev] Revisions that cause buildbot problems but aren't on blame lists Hello Bill, Daniel, Could you point me to the exact build and tell me the correct revision to blame, please? Most likely, this means that your bot defines wrong dependencies. I can look in to this, once I'll learn the details. Thanks Galina On Fri, Oct 30, 2015 at 8:43 PM, Daniel Sa...

I've investigated several failures that my buildbots detected but when I figured out which revisions caused the failures they weren't on any blame lists. Thus the developer has no clue they broke anything until I contact them. It appears this happens when (for instance) one of the test cases in projects/test-suite is updated and causes a failure. Such a revision also won't kick off a new test cycle. Should the bots be including the...

...________________________________________ From: llvm-dev [llvm-dev-bounces at lists.llvm.org] on behalf of Renato Golin via llvm-dev [llvm-dev at lists.llvm.org] Sent: 30 October 2015 08:34 To: Bill Seurer Cc: LLVM Dev Subject: Re: [llvm-dev] Revisions that cause buildbot problems but aren't on blame lists On 30 October 2015 at 14:48, Bill Seurer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > It appears this happens when (for instance) one of the test cases in > projects/test-suite is updated and causes a failure. Such a revision also > won't kick off a new test cycle....

...objects. On Mon, Oct 6, 2014 at 3:10 PM, Bruce Hoult <bruce at hoult.org> wrote: > On Tue, Oct 7, 2014 at 8:54 AM, Rui Ueyama <ruiu at google.com> wrote: > >> would touch all the lines. Diff is not powerful enough to trace the >> history beyond variable renaming. svn blame would become useless. >> > > "useless" is much too strong a description. > > If svn blame points to the reformat commit, then simply re-run the blame > on the commit before the reformat. > > If total reformats are frequent then this is impractical. If they happe...

hpa, etal, pxelinux works great from a push of the reset button. machine boots normally. However, after i issue 'reboot' command, my box fails to find the tftp server during reboot. This looks to be happening before pxelinux has any chance to participate, so it cannot be to blame. Im seeking corroboration here before I go badgering the bios-provider here's the relevant pxelinux.cfg/default, and what the bios puts out to serial SERIAL 0 19200 CONSOLE 0 DEFAULT menu.c32 NSC DP83815/DP83816 Fast Ethernet UNDI, v1.03 Copyright (C) 2002, 2003 National Semiconductor Co...

...that switching to LLVM style will cost too much if it means we are going to lose virtually all commit history. A patch to switch to LLVM style would rename all local and member variables, so it would touch all the lines. Diff is not powerful enough to trace the history beyond variable renaming. svn blame would become useless. I have no strong opinion on this. If many other LLD developers really want to make this happen, I can bear with that. It doesn't feel very productive thing to do to me, though. On Sun, Oct 5, 2014 at 2:26 PM, Tim Northover <t.p.northover at gmail.com> wrote: >...

...> I think that misses the common usage of the term "flaky test" (or do the > tests themselves end up other (1) or (2)?) or flaky tests due to flaky > product code (hash ordering in the output). Flaky code, either compiler or tests, are the ones that don't fail in the correct blame list. Otherwise, even if it was flaky, we don't know, because it failed in the right blame list, so it's easy to revert or XFAIL. So, in my categorisation, flaky code ends up in either 3 or 4: 3, wrong blame list: if the failure is completely independent from the blame list, example, misu...

...VM repo including subprojects to the new naming scheme without breaking them. > - Many projects, especially LLVM and Clang have lots of out-of-tree downstream repos. We need to provide a tool to rebase such repos to a commit after a renaming. > - The sweeping change shouldn't break `git blame`. > > What I learned from the lld's naming scheme change: > > - There are many member variables in the LLVM/lld codebase that have the same name as accessors ignoring case (i.e. many classes define foo() as an accessor to a member variable Foo). Such variables would conflict with f...

...Problem #1: What is flaky? The types of failures of a buildbot: 1. failures because of bad hardware / bad software / bad admin (timeout, disk full, crash, bad RAM) 2. failures because of infrastructure problems (svn, lnt, etc) 3. failures due to previous or external commits unrelated to the blame list (intermittent, timeout) 4. results that you don't know how to act on, but you have to 5. clear error messages, easy to act on In my view, "flaky" is *only* number 1. Everything else is signal. I agree that bots that cause 1. should be silent, and that failures in 2. and 3. shou...

...ris > > > On May 21, 2019, at 3:01 AM, Michael Platings via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi folks, > > Git is on its way to learning how to ignore commits, allowing us to do > variable renaming and other small refactorings without breaking git blame. > > It's like git-hyper-blame [1] but significantly more powerful as it uses > fuzzy matching to match lines, including lines that may have been split or > joined. > > A preview release of Git with this new feature is at: > https://github.com/mplatings/git/releases/tag/ign...

> Look at: > > https://t.co/6fT61xgtGH > > Get the latest microcode.dat file from here: > > https://t.co/zPwagbeJFY > > See how to update the microcode from the links at the bottom of this page: > > https://t.co/EOgclWdHCw > > An before anyone asks .. I have no idea why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)

On Wed, May 22, 2019 at 09:07:32AM -0600, James Szinger wrote: > On Wed, May 22, 2019 at 7:44 AM mark <m.roth at 5-cent.us> wrote: > > > > The joys of systemd.... > > I'm not sure it's right to blame systemd. Systemd asked nicely for > the service to shutdown. But we can blame systemd for the cryptic message A stop job is running Surely systemd knows what service it is waiting for, why doesn't it tell us? The stop job XYZ is running jon -- Jon H. LaBadie jcu...