please push the performance branch from class today

[michaelpalumbo]

@SquidPr0Quo can you please commit and push any changes made in your performance branch and push them asap? Thanks. If there are no changes, you probably didn't save the patch after performing it. let me know

[SquidPr0Quo]

Unfortunately, It doesn't look like there were any changes. This <https://github.com/dispersionlab/gitshow11/tree/Preformace> shows that the last commit was two days ago, which was the day I uploaded the final version for this week's edits.

…

On Tue, 21 Jan 2020 at 17:26, Michael Palumbo ***@***.***> wrote: @SquidPr0Quo <https://github.com/SquidPr0Quo> can you please commit and push any changes made in your performance branch and push them asap? Thanks. If there are no changes, you probably didn't save the patch after performing it. let me know — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AH7TQZWSQ7MFRLCNX5HLU4TQ65ZADA5CNFSM4KJ4B35KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHY2LGQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7TQZQNCCHZ3AICBYQ4IYTQ65ZADANCNFSM4KJ4B35A> .

[michaelpalumbo]

Ah. Could you  Cd to your performance branch for this week, open rack, and then save the patch? (Rack always opens the autosave state, always it's last known state). Anyway, save the patch.vcv in the performance branch, commit it then push? On Jan 21, 2020, 8:21 PM -0500, Andrew Sidsworth <notifications@github.com>, wrote: Unfortunately, It doesn't look like there were any changes. This <https://github.com/dispersionlab/gitshow11/tree/Preformace> shows that the last commit was two days ago, which was the day I uploaded the final version for this week's edits.

On Tue, 21 Jan 2020 at 17:26, Michael Palumbo ***@***.***> wrote: @SquidPr0Quo <https://github.com/SquidPr0Quo> can you please commit and push any changes made in your performance branch and push them asap? Thanks. If there are no changes, you probably didn't save the patch after performing it. let me know — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AH7TQZWSQ7MFRLCNX5HLU4TQ65ZADA5CNFSM4KJ4B35KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHY2LGQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7TQZQNCCHZ3AICBYQ4IYTQ65ZADANCNFSM4KJ4B35A> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[SquidPr0Quo]

Just did that, hopefully that worked? On Tue, 21 Jan 2020 at 22:28, Michael Palumbo <notifications@github.com> wrote:

…

Ah. Could you Cd to your performance branch for this week, open rack, and then save the patch? (Rack always opens the autosave state, always it's last known state). Anyway, save the patch.vcv in the performance branch, commit it then push? On Jan 21, 2020, 8:21 PM -0500, Andrew Sidsworth ***@***.***>, wrote: Unfortunately, It doesn't look like there were any changes. This <https://github.com/dispersionlab/gitshow11/tree/Preformace> shows that the last commit was two days ago, which was the day I uploaded the final version for this week's edits. On Tue, 21 Jan 2020 at 17:26, Michael Palumbo ***@***.***> wrote: > @SquidPr0Quo <https://github.com/SquidPr0Quo> can you please commit and > push any changes made in your performance branch and push them asap? > Thanks. If there are no changes, you probably didn't save the patch after > performing it. let me know > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #5?email_source=notifications&email_token=AH7TQZWSQ7MFRLCNX5HLU4TQ65ZADA5CNFSM4KJ4B35KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHY2LGQ >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AH7TQZQNCCHZ3AICBYQ4IYTQ65ZADANCNFSM4KJ4B35A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AH7TQZQMR547LWJ46WD73ULQ664O3A5CNFSM4KJ4B35KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJSDBKY#issuecomment-576991403>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH7TQZQZKY77GKRKTSPIYELQ664O3ANCNFSM4KJ4B35A> .